chore(manifest): refresh — last_audit 2026-05-04 → 2026-05-07; reflect recent ports#36
Merged
Merged
Conversation
…t recent ports
Manifest was 3 days stale; many endpoints listed as missing have
been ported since the last audit.
Moved from endpoints_missing → endpoints_covered (with PR refs):
- POST /v1/cues/{id}/fire (PR #23; in-flight kwargs in #33)
- POST /v1/executions/{id}/replay (PR #25)
- GET /v1/executions/claimable (PR #23)
- POST /v1/executions/{id}/claim (PR #23)
- POST /v1/executions/claim (PR #23)
- GET /v1/workers + DELETE /v1/workers/{id} (PR #26)
- GET /v1/usage (PR #26)
- POST /v1/agents + GET/PATCH/DELETE /v1/agents/{ref}
+ GET /v1/agents/{ref}/webhook-secret
+ GET /v1/agents/{ref}/inbox + /sent (PR #27)
- POST /v1/messages + GET/read/ack (PR #28)
Added in-flight refs (open PRs):
- GET /v1/agents/roster (in-flight PR #35; cueapi #630 parity)
- GET /v1/agents/{ref}/presence (in-flight PR #35; cueapi #662 parity)
- send_at + exit_criteria + idempotency_key kwargs on fire (PR #33)
- send_at kwarg on messages.send (PR #34)
New endpoints_missing items (post-audit):
- POST /v1/agents/{ref}/webhook-secret/regenerate (destructive; tracked)
- DELETE /v1/messages bulk (cueapi #650; bounded by cueapi-cli upstream)
- POST /v1/executions/{id}/live-claim (cueapi #664; handler-runtime, not SDK)
New "in_flight_ports_2026_05_07" section listing all 4 currently-open
SDK PRs with PR-overlap notes (PR #30/#33 lane-flagged with cueapi-main).
Bumped sdk_version_at_audit 0.1.3 → 0.2.x.
This refresh closes the Backlog row "Refresh cueapi-python parity-manifest.json"
filed earlier today (Self-flag 2026-05-07).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
parity-manifest.jsonwas 3 days stale. Many endpoints listed asendpoints_missinghave been ported since 2026-05-04 (notably PRs #23 / #25 / #26 / #27 / #28 added the entire fire + executions + workers + usage + agents + messages surface).This refresh moves the now-covered endpoints to
endpoints_coveredwith PR refs, adds in-flight refs for open PRs (#33 / #34 / #35), and adds three newendpoints_missingitems that emerged post-audit.Moved missing → covered (with PR refs)
POST /v1/cues/{id}/fire(PR feat: add fire + list_claimable + claim + claim_next #23; in-flight kwargs in feat(cues): add send_at + exit_criteria + idempotency_key to fire() #33)POST /v1/executions/{id}/replay(PR fix(executions): mark_verified actually sends valid+reason; add replay() #25)GET /v1/executions/claimable(PR feat: add fire + list_claimable + claim + claim_next #23)POST /v1/executions/{id}/claim(PR feat: add fire + list_claimable + claim + claim_next #23)POST /v1/executions/claim(PR feat: add fire + list_claimable + claim + claim_next #23)GET /v1/workers+DELETE /v1/workers/{id}(PR feat: add WorkersResource + UsageResource (parity with /v1/workers + /v1/usage) #26)GET /v1/usage(PR feat: add WorkersResource + UsageResource (parity with /v1/workers + /v1/usage) #26)POST /v1/agents+GET/PATCH/DELETE /v1/agents/{ref}+ webhook-secret + inbox/sent (PR feat: add AgentsResource (messaging primitive identity surface) #27)POST /v1/messages+GET/read/ack(PR feat: add MessagesResource (messaging primitive lifecycle) #28)In-flight ports added
New
in_flight_ports_2026_05_07section listing all 4 currently-open SDK PRs with PR-overlap notes (#30/#33 lane-flagged with cueapi-main):cues.fire(send_at, exit_criteria, idempotency_key)(#618 + #632 + #683)messages.send(send_at)(#623)agents.roster()+agents.presence()(#630 + #662)cues.fire(send_at)from a sibling laneNewly-missing items (post-audit)
POST /v1/agents/{ref}/webhook-secret/regenerate— destructive; tracked on BacklogDELETE /v1/messagesbulk (cueapi #650) — server-side shipped; bounded by cueapi-cli upstreamPOST /v1/executions/{id}/live-claim(cueapi #664) — handler-runtime concern, not SDK control-planeOther
sdk_version_at_audit0.1.3 → 0.2.xlast_full_audit2026-05-04 → 2026-05-07Source
Closes the Backlog row "Refresh cueapi-python parity-manifest.json (last-audit 2026-05-04, lots of recent ports)" filed earlier today (Self-flag 2026-05-07).
Pure documentation update — no code changes. Safe to merge once reviewed.
🤖 Generated with Claude Code